[release/7.0] Remove legacy check to fix Runtime SiteExtension #46045
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #46033 to release/7.0
/cc @BrennanConroy
Remove legacy check to fix Runtime SiteExtension
Summary of the changes (Less than 80 chars)
Description
This package bundles the Runtime and ANCM and then modifies the web.config in App Service to use the bundled versions. A change in infrastructure in 7.0.1 caused the package to no longer bundle the Runtime.
Customer Impact
Azure App Service reported a customer complaining about the 7.0.1 package no longer functioning.
Regression?
7.0.0 builds set a legacy setting, starting in 7.0.1 the setting was no longer set. Something about arcade changes that removed the legacy variable.
Risk
We were just getting lucky before that a legacy setting was set in our builds that allowed the package to be built correctly. This removes the reliance on the setting, nothing else about the package being built changed.
Verification
Packaging changes reviewed?